Communication control method

ABSTRACT

A communication method, first communication apparatus, and chipset included in a first communication apparatus function to receive from a base station first information indicating that the base station supports a relay apparatus configured to relay traffic between the base station and another communication apparatus, transmit to the base station, after receiving the first information from the base station, second information indicating that the first communication apparatus is the relay apparatus, and transmit to the base station, by the first communication apparatus, third information indicating expected data amount of the first communication apparatus. Abase station is configured to transmit the first information to the first communication apparatus, thereafter receive the second information, and receive the third information.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a Continuation Application of U.S. patentapplication Ser. No. 16/281,909, filed Feb. 21, 2019, which is aContinuation Application of U.S. patent application Ser. No. 15/469,314,filed Mar. 24, 2017, which is a Continuation Application of U.S. patentapplication Ser. No. 14/386,407, filed Sep. 19, 2014, which is the U.S.National Phase Application of International Application No.PCT/JP2013/058143, filed Mar. 21, 2013, which claims benefit of U.S.Provisional Application Nos. 61/615,045, 61/615,059, 61/615,067,61/615,073 and 61/615,087, all filed Mar. 23, 2012, the entire contentsof which are incorporated herein by reference.

TECHNICAL FIELD

The present disclosure relates to a communication control method in amobile communication system.

BACKGROUND ART

In 3GPP (3rd Generation Partnership Project) which is a project aimingto standardize a mobile communication system, specifications of a relaystation have been designed.

The relay station performs relay transmission between a donor basestation and a user terminal (for example, refer to Non Patent Literature1).

PRIOR ART DOCUMENT Non-Patent Document

[Non-patent Document 1] 3GPP technology specifications “TS 36.300 V11.0. 0” December, 2011

SUMMARY

A communication method according to the present disclosure comprisesreceiving from a base station, by a first communication apparatus, firstinformation indicating that the base station supports a relay apparatusconfigured to relay traffic between the base station and anothercommunication apparatus. The communication method comprises the firstcommunication apparatus transmitting to the base station, afterreceiving the first information from the base station, secondinformation indicating that the first communication apparatus is therelay apparatus, and transmitting to the base station third informationindicating expected data amount of the first communication apparatus.

A first communication apparatus according to the present disclosurecomprises a processor and a memory coupled to the processor. Theprocessor is configured to perform process of receiving, from a basestation, first information indicating that the base station supports arelay apparatus configured to relay traffic between the base station andanother communication apparatus. The processor is configured to performthe process of transmitting to the base station, after receiving thefirst information from the base station, second information indicatingthat the first communication apparatus is the relay apparatus, and theprocess transmitting to the base station, third information indicatingexpected data amount of the first communication apparatus.

A base station according to the present disclosure comprises a processorand a memory coupled to the processor. The processor is configured toperform the process of transmitting to a first communication apparatus,first information indicating that the base station supports a relayapparatus configured to relay traffic between the base station andanother communication apparatus. The processor is configured to performthe process of receiving from the first communication apparatus, aftertransmitting the first information, second information indicating thatthe first communication apparatus is the relay apparatus, and theprocess of receiving from the first communication apparatus thirdinformation indicating expected data amount of the first communicationapparatus.

A chipset according to the present disclosure is included in a firstcommunication apparatus, and comprises a processor and a memory coupledto the processor. The processor configured to perform process ofreceiving, from a base station, first information indicating that thebase station supports a relay apparatus configured to relay trafficbetween the base station and another communication apparatus. Theprocessor is configured to perform the process of transmitting to thebase station, after receiving the first information from the basestation, second information indicating that the first communicationapparatus is the relay apparatus, and the process of transmitting to thebase station, third information indicating expected data amount of thefirst communication apparatus.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a configuration diagram of a mobile communication system.

FIG. 2 is a protocol stack diagram of a Un interface.

FIG. 3 is a protocol stack diagram of an X2 interface.

FIG. 4 is a protocol stack diagram of an S1 interface.

FIG. 5 is a configuration diagram of a radio frame.

FIG. 6 is a block diagram of UE.

FIG. 7 is a block diagram of eNB.

FIG. 8 is a block diagram of MRN.

FIG. 9 is a sequence diagram of an operation pattern 1 according to afirst embodiment.

FIG. 10 is a sequence diagram of an operation pattern 2 according to thefirst embodiment.

FIG. 11 is a sequence diagram of an operation pattern 3 according to thefirst embodiment.

FIG. 12 is a sequence diagram of an operation pattern 1 according to asecond embodiment.

FIG. 13 is a sequence diagram of an operation pattern 2 according to thesecond embodiment.

FIG. 14 is a configuration diagram of a DeNB list used in an operationpattern 4 according to the second embodiment.

FIG. 15 is a sequence diagram of an operation pattern 1 according to athird embodiment.

FIG. 16 is a sequence diagram of an operation pattern 2 according to thethird embodiment.

FIG. 17 is a configuration diagram of a neighboring eNB list accordingto a fourth embodiment.

FIG. 18 is a sequence diagram of an operation pattern 1 according to thefourth embodiment.

FIG. 19 is a sequence diagram of an operation pattern 2 according to thefourth embodiment.

FIG. 20 is an operation sequence diagram according to a fifthembodiment.

DESCRIPTION OF EMBODIMENTS Overview of Embodiment

A communication control method of the first embodiment is acommunication control method in a relay station that holds a donor basestation list, is connected to a donor base station existing on the donorbase station list, and performs relay transmission between the donorbase station and a user terminal, and comprises a step A of designatinga neighboring base station, a step B of inquiring the neighboring basestation designated in the step A of whether to accept or refuse therelay station, and a step C of updating the donor base station list inresponse to an inquiry result in the step B.

In the first embodiment, the step B may comprise a step B1 of inquiringthe neighboring base station designated in the step A of whether theneighboring base station has a donor base station function.

In the first embodiment, the step B may comprise a step B2 of notifyingthe neighboring base station designated in the step A of a load state ofthe relay station.

In the first embodiment, the communication control method may furthercomprise a step D of notifying a core network device of the donor basestation list updated in the step C through the donor base station.

A communication control method according to the second and forthembodiments is a communication control method applied to a mobilecommunication system including a relay station that performs relaytransmission between a donor base station and a user terminal, andcomprises a step A of, in a handover procedure of the relay station to atarget base station, transmitting a handover request for requesting toaccept the relay station, to the target base station, wherein in thestep A, information indicating a load state of the relay station istransmitted, together with the handover request.

In the second embodiment, when the handover to the target base stationis determined at the relay station, in the step A, the relay station maytransmit the information indicating the load state of the relay station,together with the handover request.

In the second embodiment, the communication control method may furthercomprise a step C of determining, by the relay station, prior to thestep A, the target base station, on the basis of a donor base stationlist that is a list of base stations of a donor base station candidateor a neighboring base station list that is a list of neighboring basestations, wherein the donor base station list or the neighboring basestation list includes information on at least one of: a position, a celldirection, a capacity, and a cell size, regarding each of the basestations of a donor base station candidate or the neighboring basestations.

In the fourth embodiment, when the handover to the target base stationis determined at the donor base station, in the step A, the donor basestation may transmit the information indicating the load state of therelay station, together with the handover request.

A communication control method according to the third embodiment is acommunication control method in a mobile communication system includinga relay station that holds a donor base station list, is connected to adonor base station existing on the donor base station list, and performsrelay transmission between the donor base station and a user terminal,and comprises a step A of obtaining, by the relay station, when it isnot possible to perform a handover of the relay station to the basestation existing on the donor base station list, a donor base stationlist held by another relay station connected to a predetermined basestation, from the other relay station.

In the third embodiment, the communication control method may furthercomprise a step C of receiving, by the relay station, prior to the stepA, relay station information that is information on another relaystation connected to the predetermined base station, from thepredetermined base station.

In the third embodiment, the communication control method furthercomprises a step D of transmitting a handover request from the relaystation to a target base station; and a step E of transmitting, by thetarget base station, a handover rejection response to the relay station,when rejecting the handover request, wherein the predetermined basestation is the target base station, in the step E, the target basestation transmits the handover rejection response including the relaystation information, and in the step C, the relay station may receivethe relay station information included in the handover rejectionresponse.

In the third embodiment, the communication control method may furthercomprise a step D of inquiring, prior to the step C, the predeterminedbase station of another relay station connected to the predeterminedbase station.

A communication control method according to the fourth embodiment is acommunication control method applied to a mobile communication systemincluding a base station that has a donor base station function and arelay station that performs relay transmission between the base stationand a user terminal, and comprises: a step A of, by the base station,holding a neighboring base station list including an identifier of aneighboring base station, wherein the neighboring base station listfurther includes information indicating whether or not the neighboringbase station has a donor base station function, regarding each of theneighboring base stations.

In the fourth embodiment, the communication control method furthercomprises: a step B of requesting, by the base station, information forupdating the neighboring base station list, to a core network device,when the relay station is connected to the base station, and a step C ofupdating, by the base station, the neighboring base station list inresponse to the information from the core network device.

In the fourth embodiment, the communication control method furthercomprises: a step D of receiving, by the target base station, a handoverrequest from the base station in a handover procedure of the relaystation from the base station to the target base station, and a step Eof transmitting, by the target base station, information indicating thatthe target base station does not have the donor base station function,together with a rejection response to the handover request, to the basestation when the target base station does not have the donor basestation function.

A communication control method according to the second and fifthembodiments is a communication control method applied to a mobilecommunication system in which a handover of a user terminal connected toa base station is determined by the base station, and comprises: a stepA of performing a handover determination of a relay station that isconnected to a donor base station and performs relay transmissionbetween the donor base station and a user terminal, wherein in the stepA, the handover determination of the relay station is performed by therelay station.

In the second and fifth embodiments, the communication control methodfurther comprises a step B of transmitting, by the relay station, ahandover request for requesting to accept the relay station, when, as aresult of the step A, determining that the handover to the target basestation is performed.

In the second embodiment, the step B includes a step B1 of transmitting,by the relay station, the handover request to the target base station,by using a network interface established between the relay station andthe target base station.

In the second embodiment, the communication control method furthercomprises: a step C of requesting, by the target base station,information for the handover of the relay station, to the donor basestation, in response to reception of the handover request from the relaystation; and a step D of transmitting, by the donor base station, theinformation for the handover of the relay station, to the target basestation, in response to the request from the target base station.

In the second embodiment, the communication control method furthercomprises a step E of transmitting, by the target base station, ahandover permission response including the information for the handoverof the relay station, to the relay station, by using the networkinterface, after receiving the information for the handover of the relaystation, from the donor base station.

In the second embodiment, in the step B, the relay station transmits thehandover request to the donor base station, after including one or aplurality of identifiers of the target base station in the handoverrequest.

In the second and fifth embodiments, the communication control methodfurther comprises, a step of inquiring, prior to the step B, by therelay station, the donor base station and/or the target base station ofwhether or not possible to respond to a handover request from the relaystation.

(1) First Embodiment

In the present embodiment, an example of a mobile communication systemconfigured on the basis of 3GPP standards (that is, LTE-Advanced) afterrelease 10 will be described.

(1.1) Overview of the Mobile Communications System

FIG. 1 is a configuration diagram of a mobile communication systemaccording to the present embodiment. As illustrated in FIG. 1, themobile communication system includes a user terminal (UE: UserEquipment) 100, a base station (eNB: evolved Node-B) 200, a movablerelay station (MRN: Mobile Relay Node) 300, a mobility management device(MME: Mobility Management Entity)/a gateway device (S-GW: ServingGateway) 400, and an operation and maintenance device (OAM: Operationand Maintenance) 500.

The eNB 200 and the MRN 300 are network devices included in a radioaccess network (E-UTRAN: Evolved-UMTS Terrestrial Radio Access Network)10. The MME/S-GW 400 and the OAM 500 are network devices included in acore network (EPC: Evolved Packet Core) 20.

The UE 100 is a movable radio communication device owned by a user. TheUE 100 performs radio communication with a cell (called a “servingcell”), with which a connection is established, in a connected statecorresponding to a state during communication.

In addition, the “cell” is used as a term indicating a minimum unit of aradio communication area, and is also used as a function of performingradio communication with the UE 100. Thus, the eNB 200 is also called acell.

When the UE 100 moves together with the movement of a user, a change inthe serving cell of the UE 100 is necessary. An operation, in which theUE 100 changes the serving cell in a connected state, is called“handover”. A series of procedures of the handover are called a“handover procedure”. The handover procedure includes a handoverpreparation step (Preparation), a handover execution step (Execution),and a handover completion step (Completion).

In the handover procedure, a cell of a handover source is called a“source cell” and a cell of a handover destination is called a “targetcell”. Furthermore, in the handover procedure from a certain eNB 200 (acell) to another eNB 200 (a cell), an eNB 200 of a handover source iscalled a “source eNB” and an eNB 200 of a handover destination is calleda “target eNB”.

The eNB 200 is a stationary radio communication device installed by acommunication provider, and for example, is a macro base station (MeNB)or a pico base station (PeNB). Alternatively, the eNB 200 may be a homebase station (HeNB) installable within the house. The eNB 200 forms acell. The eNB 200 performs radio communication with the UE 100.

The eNB 200 has a decision right of handover for the UE 100 subordinateto the eNB 200. Specifically, the eNB 200 determines whether to performhandover from a serving cell to another cell on the basis of ameasurement report from the UE 100. The eNB 200 holds a list(hereinafter, a “neighboring eNB list”) of neighboring eNBs (neighboringcells) in order to control the handover of the UE 100.

When the eNB 200 has a donor base station (DeNB) function, the eNB 200is able to establish a connection to the MRN 300 and to operate as adonor of the MRN 300. For example, an eNB 200 supporting a release after3GPP release 10 has the DeNB function as an option function, but an eNB200 supporting a release before the 3GPP release 10 does not have theDeNB function. Alternatively, an eNB 200 (HeNB) with low processingcapability may not have the DeNB function.

The eNB 200 communicates with the EPC 20 (MME/S-GW 400) through an S1interface that is a logical communication channel between the eNB 200and the EPC 20. Furthermore, the S1 interface is also establishedbetween the MRN 300 and the eNB 200 (DeNB 200-1) operating as the donorof the MRN 300. The MRN 300 is able to communicate with the EPC 20through the S1 interface via the DeNB 200-1.

The MME is provided corresponding to a control plane dealing withcontrol information, and performs various types of mobility managementor verification processes for the UE 100. The S-GW is providedcorresponding to a user plane dealing with user data, and performsforwarding control and the like of user data transmitted/received by theUE 100.

The eNB 200 communicates with a neighboring eNB 200 through an X2interface that is a logical communication channel between the eNB 200and the neighboring eNB 200. Furthermore, the X2 interface is alsoestablished between the MRN 300 and the eNB 200 (DeNB 200-1) operatingas the donor of the MRN 300. The MRN 300 is able to communicate with aneighboring eNB 200-2 through the X2 interface via the DeNB 200-1.

In the present embodiment, the S1 interface and/or the X2 interfacecorrespond to a network interface.

The MRN 300 is a movable radio communication device installed in amoving body such as a train or a bus. The MRN 300 holds a list(hereinafter, a “DeNB list”) of eNBs 200 (cells) available as DeNBs. TheMRN 300 acquires the DeNB list from the OAM 500 at the time of startingof the MRN 300.

The MRN 300 establishes (Connect) a connection to an eNB 200 existing onthe DeNB list, and performs radiocommunication with the eNB 200 (theDeNB 200-1) with which a connection is established. Then, the MRN 300performs relay transmission between the UE 100 subordinate to the MRN300 and the DeNB 200-1.

Basically, the MRN 300 is equal to the UE 100 in terms of the DeNB 200-1and is equal to the eNB 200 in terms of the UE 100. That is, the MRN 300has both a characteristic of the UE 100 and a characteristic of the eNB200.

When the MRN 300 moves together with the movement of a movable body, itis necessary for the MRN 300 to be transitioned (Disconnect) from aconnected state to an idle state and then to establish (Connect) aconnection to a new DeNB, or to establish (that is, handover) aconnection to the new DeNB while maintaining the connected state. In thepresent embodiment, the former case (Connect/Disconnect) is consideredand the latter case (handover) will be described after the secondembodiment.

The MRN 300 has a decision right of handover for the UE 100 subordinateto the MRN 300. Specifically, the MRN 300 determines whether to performhandover from a serving cell to another cell on the basis of themeasurement report (Measurement Report) from the UE 100. The eNB 200holds the neighboring eNB list in order to control the handover of theUE 100.

Next, a protocol stack associated with the MRN 300 will be described.FIG. 2 is a protocol stack diagram of a Un interface.

As illustrated in FIG. 2, in the protocol stack of the Un interface, alayer 1 is a physical (PHY) layer. The layer 2 includes a MAC (MediumAccess Control) layer, an RLC (Radio Link Control) layer, and a PDCP(Packet Data Convergence Protocol) layer. The layer 3 includes an RRC(Radio Resource Control) layer.

The PHY layer performs data coding/decoding, modulation/demodulation,antenna mapping/demapping, and resource mapping/demapping. The PHY layerprovides a transmission service to an upper layer using a physicalchannel. Between a physical layer of the MRN 300 and a physical layer ofthe DeNB 200-1, data is transmitted through a physical channel. The PHYlayer is connected to the MAC layer through a transport channel.

The MAC layer performs preferential control of data, and aretransmission process and the like by hybrid ARQ (HARQ). Between a MAClayer of the MRN 300 and a MAC layer of the DeNB 200-1, data istransmitted through a transport channel. The MAC layer of the DeNB 200-1includes MAC scheduler for decision of transport formats and resourceblocks of an uplink and a downlink. The transport format includes atransport block size, a modulation/coding scheme (MCS), and antennamapping.

The RLC layer transmits data to an RLC layer of a reception side usingthe functions of the MAC layer and the PHY layer. Between an RLC layerof the MRN 300 and an RLC layer of the DeNB 200-1, data is transmittedthrough a logical channel.

The PDCP layer performs header compression/extension andencryption/decryption.

The RRC layer is defined only in a control plane. Between an RRC layerof the MRN 300 and an RRC layer of the DeNB 200-1, data is transmittedthrough a radio bearer. The RRC layer controls the logical channel, thetransport channel, and the physical channel in response toestablishment, re-establishment, and release of the radio bearer. Whenthere is an RRC connection between the RRC of the MRN 300 and the RRC ofthe DeNB 200-1, the MRN 300 is in a “connected state”, and otherwise,the MRN 300 is in an “idle state”.

A NAS (Non-Access Stratum) layer positioned above the RRC layer isprovided in the MRN 300 and the MME 300 to perform session management,mobility management and the like.

FIG. 3 is a protocol stack diagram for the X2 interface establishedbetween the MRN 300 and the neighboring eNB 200-2. Hereinafter, acontrol plane will be described.

As illustrated in FIG. 3, IP (Internet Protocol) and SCTP (Stream.Control Transmission Protocol) are provided on a layer 1 (L1) and alayer 2 (L2), and X2-AP (X2 Application Protocol) is provided on theSCTP. The X2-AP transmits and receives a message according to handoverand the like.

An X2 message transmitted by the MRN 300 may be relayed by the DeNB200-1 and transmitted to the neighboring eNB 200-2. Furthermore, an X2message transmitted by the neighboring eNB 200-2 may be relayed by theDeNB 200-1 and transmitted to the MRN 300.

L1 and L2 between the MME 300 and the DeNB 200-1 are equal to L1 and L2of the Un interface.

FIG. 4 is a protocol stack diagram for the S1 interface establishedbetween the MRN 300 and the MME 400. As illustrated in FIG. 4, the S1interface is different from the X2 interface in that S1-AP is providedinstead of the X2-AP.

FIG. 5 is a configuration diagram of a radio frame used in the mobilecommunication system (an LTE system) according to the presentembodiment. The LTE system employs OFDMA (Orthogonal Frequency DivisionMultiplexing Access) in a downlink and SC-FDMA (Single Carrier FrequencyDivision Multiple Access) in an uplink.

As illustrated in FIG. 5, the radio frame includes 10 subframes arrangedin a time-period direction, wherein each subframe includes two slotsarranged in the time-period direction. Each subframe has a length of 1ms and each slot has a length of 0.5 ms. Each subframe includes aplurality of resource blocks (RBs) in a frequency direction, and aplurality of symbols in the time-period direction. Each symbol isprovided at a head thereof with a guard interval called a cyclic prefix(CP).

In the downlink, an interval of several symbols at the head of eachsubframe is a control region mainly used as a physical downlink controlchannel (PDCCH). Furthermore, the other interval of each subframe is adata region mainly used as a physical downlink shared channel (PDSCH).In the downlink, reference signals (RS) different from each other ineach cell are transmitted.

In the uplink, both end portions in the frequency direction of eachsubframe are control regions mainly used as a physical uplink controlchannel (PUCCH). Furthermore, the center portion in the frequencydirection of each subframe is a data region mainly used as a physicaluplink shared channel (PUSCH).

The radio frame includes a plurality of MBSFN (MBMS Single FrequencyNetwork) subframes. The MRN 300 communicates with the DeNB 200-1 usingthe MBSFN subframes.

(1.2) Block Configuration

Hereinafter, the block configurations of the UE 100, the eNB 200, andthe MRN 300 will be described.

FIG. 6 is a block diagram of the UE 100. As illustrated in FIG. 6, theUE 100 includes a radio transmission/reception unit 110, a storage unit120, and a control unit 130.

The radio transmission/reception unit 110 transmits/receives a radiosignal.

The storage unit 120 stores various types of information that is usedfor the control by the control unit 130.

The control unit 130 controls various functions of the UE 100. Forexample, the control unit 130 controls the aforementioned operations ofthe UE 100.

FIG. 7 is a block diagram of the eNB 200. As illustrated in FIG. 7, theeNB 200 includes a radio transmission/reception unit 210, a networkcommunication unit 220, a storage unit 230, and a control unit 240.

The radio transmission/reception unit 210 transmits/receives a radiosignal. Furthermore, the radio transmission/reception unit 210 forms acell.

The network communication unit 220 communicates with the MME/S-GW 400through the S1 interface. The network communication unit 220communicates with the neighboring eNB 200 through the X2 interface.

The storage unit 230 stores various types of information that is usedfor the control by the control unit 240. Furthermore, the storage unit230 stores (holds) the neighboring eNB list.

The control unit 240 controls various functions of the eNB 200. Forexample, the control unit 240 controls the aforementioned operations ofthe eNB 200 and operations of the eNB 200 which will be described later.

FIG. 8 is a block diagram of the MRN 300. As illustrated in FIG. 8, theMRN 300 includes a radio transmission/reception unit 310 for eNB, aradio transmission/reception unit 320 for UE, a storage unit 330, and acontrol unit 340.

The radio transmission/reception unit 310 for eNB receives a radiosignal from the eNB 200 and transmits a radio signal to the eNB 200.

The radio transmission/reception unit 320 for UE receives a radio signalfrom the UE 100 and transmits a radio signal to the UE 100. The radiotransmission/reception unit 320 for UE forms a cell.

The storage unit 330 stores various types of information that is usedfor the control by the control unit 340. Furthermore, the storage unit330 stores (holds) the neighboring eNB list for controlling the handoverof the UE 100, and the DeNB list for deciding DeNB with which the MRN300 should establish a connection.

The control unit 340 controls various functions of the MRN 300. Forexample, the control unit 340 controls the aforementioned operations ofthe MRN 300 and operations of the MRN 300 which will be described later.The control unit 340 is able to decide a DeNB candidate in the DeNB listas DeNB by measuring the radio signal (a reference signal) received inthe radio transmission/reception unit 310 for eNB.

Furthermore, the MRN 300 may have a positioning system (for example, aGPS receiver 350) for acquiring its own location information. The MRN300 is able to estimate its own movement speed on the basis of its ownlocation information.

(1.3) Operation According to First Embodiment

Hereinafter, the operation of the mobile communication system accordingto the present embodiment will be described.

In the following operation patterns 1 to 3, the MRN 300, which holds theDeNB list, is connected to the DeNB 200-1 existing on the DeNB list, andperforms relay transmission between the DeNB 200-1 and the UE 100,designates a neighboring eNB 200, inquires the designated neighboringeNB 200 whether to accept or refuse the MRN 300, and updates the DeNBlist in response to an inquiry result.

Specifically, in the following operation patterns 1 and 2, the MRN 300designates a neighboring eNB 200 not existing on the DeNB list. When theinquiry result for the designated neighboring eNB 200 indicatespermission of the acceptance of the MRN 300, the MRN 300 updates theDeNB list such that the designated neighboring eNB 200 is added.

On the other hand, in the following operation pattern 3, the MRN 300designates a neighboring eNB 200 existing on the DeNB list. When theinquiry result for the designated neighboring eNB 200 indicates refusalof the acceptance of the MRN 300, the MRN 300 updates the DeNB list suchthat the designated neighboring eNB 200 is invalid (excluded).

(1.3.1) Operation Pattern 1

FIG. 9 is a sequence diagram of an operation pattern 1 according to thepresent embodiment.

As illustrated in FIG. 9, in step S101, the OAM 500 notifies the MRN 300of the neighboring eNB list (NL) for controlling the handover of the UE100 via the DeNB 200-1. As well as the whole of the neighboring eNBlist, only a part of the changed neighboring eNB list may be notified.

In step S102, the MRN 300 updates a held neighboring eNB list (NL) bythe neighboring eNB list received from the OAM 500.

In step S103, the MRN 300 compares the neighboring eNB list updated instep S102 with the held neighboring eNB list. Specifically, the MRN 300searches for a neighboring eNB existing on the neighboring eNB list andnot existing on the DeNB list.

Hereinafter, a description will be given on the assumption that the eNB200-2 is designated as the neighboring eNB existing on the neighboringeNB list and not existing on the DeNB list.

In step S104, the MRN 300 inquires the eNB 200-2 designated in step S103of whether the eNB 200-2 has a DeNB function through the X2 interface.

In step S105, the eNB 200-2 confirms whether the eNB 200-2 has the DeNBfunction in response to the inquiry from the MRN 300.

In step S106, the eNB 200-2 notifies the MRN 300 of whether the eNB200-2 has the DeNB function through the X2 interface.

In step S107, the MRN 300 confirms whether the eNB 200-2 has the DeNBfunction.

When the eNB 200-2 has the DeNB function (step S107; Yes), the MRN 300updates the DeNB list such that the eNB 200-2 is added in step S108.Specifically, the MRN 300 adds an identifier (a cell ID) of the eNB200-2 to the DeNB list.

In step S109, the MRN 300 notifies the OAM 500 of the DeNB list updatedin step S108 via the DeNB 200-1. As well as the whole of the updatedDeNB list, only a part of the updated DeNB list may be notified.

In addition, in the present case, the description was provided for thecase of starting the operation for updating the DeNB list by using theupdate of the neighboring eNB list as a trigger. However, instead ofsuch a method, the following method may be employed.

In the situation in which the MRN 300 stops, the necessity of updatingthe DeNB list is low. Therefore, it may be possible to start theoperation for updating the DeNB list by using the generation of atrigger of a measurement report (Measurement Report) in the MRN 300 as atrigger. Alternatively, the operation may be regularly performed in aperiod in which a movement speed of the MRN 300 exceeds a thresholdvalue.

Furthermore, by using, as a trigger, the fact that a neighboring cell (aneighboring eNB) detected by measuring a received reference signal isnot included in the DeNB list or a neighboring cell (a neighboring eNB)with the highest reference signal received power (RSRP) through themeasurement of the received reference signal is not included in the DeNBlist, the MRN 300 may start the operation for updating the DeNB list andinquire the neighboring cell (the neighboring eNB).

(1.3.2) Operation Pattern 2

FIG. 10 is a sequence diagram of an operation pattern 2 according to thepresent embodiment.

As illustrated in FIG. 10, in step S111, the OAM 500 notifies the MRN300 of the neighboring eNB list for controlling the handover of the UE100 via the DeNB 200-1. As well as the whole of the neighboring eNBlist, only a part of the changed neighboring eNB list may be notified.

In step S112, the MRN 300 updates a held neighboring eNB list by theneighboring eNB list received from the OAM 500.

In step S113, the MRN 300 compares the neighboring eNB list updated instep S112 with the held neighboring eNB list. Specifically, the MRN 300searches for a neighboring eNB existing on the neighboring eNB list andnot existing on the DeNB list.

Hereinafter, a description will be given on the assumption that the eNB200-2 is designated as the neighboring eNB existing on the neighboringeNB list and not existing on the DeNB list.

The MRN 300 recognizes its own load state. The load state includes thenumber of UEs 100 accommodated by the MRN 300 (specifically, the numberof UEs 100 being connected to the MRN 300), the amount of traffic dealtby the MRN 300, or the like. In addition, as well as an actual loadstate, a potential load state (for example, processing capability suchas the maximum number of UEs 100 that maybe accommodated or the maximumamount of traffic) may be recognized.

In step S114, the MRN 300 notifies the eNB 200-2 designated in step S113of the load state through the X2 interface and inquires the eNB 200-2 ofwhether to accept or refuse the MRN 300. At this time, it may bepossible also for the MRN 300 to notify that it is the “MRN” thatperformed the inquiry.

In step S115, the eNB 200-2 determines the acceptance or refusal of theMRN 300 in response to the inquiry from the MRN 300. Specifically, theeNB 200-2 compares a margin based on its own load state with the loadstate of the MRN 300, and determines whether a problem does not occurafter a connection to the MRN 300 is established.

In step S116, the eNB 200-2 notifies the MRN 300 of the acceptance orrefusal of the MRN 300 through the X2 interface.

In step S117, the MRN 300 confirms whether an inquiry result for the eNB200-2 is “acceptance permission” or “acceptance refusal”.

In the case of the “acceptance permission” (step S117; Yes), the MRN 300updates the DeNB list such that the eNB 200-2 is added in step S118.Specifically, the MRN 300 adds an identifier (a cell ID) of the eNB200-2 to the DeNB list.

In step S119, the MRN 300 notifies the OAM 500 of the DeNB list updatedin step S118 via the DeNB 200-1. As well as the whole of the updatedDeNB list, only a part of the updated DeNB list may be notified.

In addition, in the present case, the description was provided for thecase of starting the operation for updating the DeNB list by using theupdate of the neighboring eNB list as a trigger. However, another methoddescribed in the operation pattern 1 may be employed.

(1.3.3) Operation Pattern 3

FIG. 11 is a sequence diagram of an operation pattern 3 according to thepresent embodiment.

As illustrated in FIG. 11, in step S121, the MRN 300, for example,searches for a neighboring eNB existing on the neighboring eNB list byusing a large change in its own load state as a trigger. Hereinafter, adescription will be given on the assumption that the eNB 200-2 isdesignated as the neighboring eNB existing on the neighboring eNB list.

The MRN 300 recognizes its own load state. The load state is the numberof UEs 100 accommodated by the MRN 300 (specifically, the number of UEs100 being connected to the MRN 300), the amount of traffic dealt by theMRN 300, or the like.

In step S122, the MRN 300 notifies the eNB 200-2 designated in step S121of the load state through the X2 interface and inquires the eNB 200-2 ofwhether to accept or refuse the MRN 300. At this time, it may bepossible also for the MRN 300 to notify that it is the “MRN” thatperformed the inquiry.

In step S123, the eNB 200-2 determines the acceptance or refusal of theMRN 300 in response to the inquiry from the MRN 300. Specifically, theeNB 200-2 compares a margin based on its own load state with the loadstate of the MRN 300, and determines whether a problem does not occurafter a connection to the MRN 300 is established.

In step S124, the eNB 200-2 notifies the MRN 300 of the acceptance orrefusal of the MRN 300 through the X2 interface.

In step S125, the MRN 300 confirms whether an inquiry result for the eNB200-2 is “acceptance permission” or “acceptance refusal”.

In the case of the “acceptance refusal” (step S125; Yes), the MRN 300updates the DeNB list such that the eNB 200-2 is invalid in step S126.Specifically, the MRN 300 excludes an identifier (a cell ID) of the eNB200-2 from the DeNB list, or sets the eNB 200-2 to be temporarilyinvalid.

In step S127, the MRN 300 notifies the OAM. 500 of the DeNB list updatedin step S126 via the DeNB 200-1. As well as the whole of the updatedDeNB list, only a part of the updated DeNB list may be notified.

In addition, in the present case, the description was provided for thecase of starting the operation for updating the DeNB list by using theupdate of the neighboring eNB list as a trigger. However, another methoddescribed in the operation pattern 1 may be employed.

(1.4) Conclusion of First Embodiment

As described above, the MRN 300, which holds the DeNB list, is connectedto the DeNB 200-1 existing on the DeNB list, and performs relaytransmission between the DeNB 200-1 and the UE 100, designates aneighboring eNB 200, inquires the designated neighboring eNB 200 ofwhether to accept or refuse the MRN 300, and updates the DeNB list inresponse to an inquiry result. In this way, even when the MRN 300 moves,it is possible to allow the DeNB list to be adapted to the state of amovement destination.

In the operation patterns 1 and 2, the MRN 300 designates a neighboringeNB 200 not existing on the DeNB list. When the inquiry result for thedesignated neighboring eNB 200 indicates permission of the acceptance ofthe MRN 300, the MRN 300 updates the DeNB list such that the designatedneighboring eNB 200 is added. In this way, as a movement result of theMRN 300, when a DeNB candidate capable of accepting the MRN 300 appearsin the vicinity of the MRN 300, it is possible to add the new DeNBcandidate to the DeNB list.

In the operation pattern 3, the MRN 300 designates a neighboring eNB 200existing on the DeNB list. When the inquiry result for the designatedneighboring eNB 200 indicates refusal of the acceptance of the MRN 300,the MRN 300 updates the DeNB list such that the designated neighboringeNB 200 is invalid. In this way, when one of DeNB candidates existing onthe DeNB list does not accept the MRN 300, it is possible to exclude aneNB 20, which is not able to accept the MRN 300, from the DeNBcandidates.

Furthermore, the inquiry includes information indicating that an inquirysource is “MRN”. In this way, the neighboring eNB 200 recognizes thatthe inquiry source is “MRN” and then is able to determine the acceptanceor refusal.

The MRN 300 designates a neighboring eNB 200 not existing on the DeNBlist on the basis of a result obtained by comparing the neighboring eNBlist notified from the OAM 500 via the DeNB 200-1 with the DeNB listheld in the MRN 300. In this way, it is possible to appropriatelydesignate the neighboring eNB 200 not existing on the DeNB list.

Alternatively, the MRN 300 designates a neighboring eNB 200 not existingon the DeNB list on the basis of a radio signal received in the MRN 300from the neighboring eNB 200. In this way, it is possible toappropriately designate the neighboring eNB 200 not existing on the DeNBlist.

In the operation pattern 1, the MRN 300 inquires the designatedneighboring eNB 200 of whether the neighboring eNB 200 has the DeNBfunction. In this way, it is possible to add only the neighboring eNB200 having the DeNB function to the DeNB list.

In the operation patterns 2 and 3, the MRN 300 notifies the designatedneighboring eNB 200 of the load state of the MRN 300. In this way, theneighboring eNB 200 is able to determine whether it is possible toaccept the MRN 300 on the basis of its own load state and the load stateof the MRN 300.

The MRN 300 notifies the OAM 500 of the whole or an updated part of theupdated DeNB list via the DeNB 200-1. In this way, the OAM 500 is ableto notify another MRN 300 around the DeNB 200-1 of the updated DeNBlist. Thus, the other MRN 300 is able to use an optimized DeNB list.Alternatively, the OAM 500 may hold the DeNB list as back-up and notifythe MRN 300 of the DeNB list according to necessity.

(2) Second Embodiment

Hereinafter, the second embodiment will be described while focusing onthe differences from the aforementioned first embodiment.

In the present embodiment, an operation when the MRN 300 performshandover using the aforementioned DeNB list will be mainly described.

(2.1) Operation According to Second Embodiment

Hereinafter, the operation of the mobile communication system accordingto the present embodiment will be described.

In the following operation patterns 1 to 4, in a mobile communicationsystem in which the eNB 200 performs determination regarding thehandover of the UE 100 connected to the eNB 200, the MRN 300, which isconnected to the DeNB 200-1 and performs relay transmission between theDeNB 200-1 and the UE 100, performs determination regarding the handoverof the MRN 300. Then, the MRN 300 transmits a handover request to atarget eNB 200 using the X2 interface that is established between theMRN 300 and the target eNB 200.

(2.1.1) Operation Pattern 1

FIG. 12 is a sequence diagram of the operation pattern 1 according tothe embodiment. In an initial state of the present sequence, it isassumed that the MRN 300 is being connected to the DeNB 200-1 to performrelay transmission.

As illustrated in FIG. 12, in step S200, the MRN 300 checks ameasurement result of a received reference signal and a held DeNB list.

In step S201, the MRN 300 performs handover determination in response toa check result in step S200. For example, when a DeNB candidate withRSRP higher than that of a DeNB 200-1 during current connection existson the DeNB list, the MRN 300 decides the DeNB candidate as a targeteNB.

Hereinafter, a description will be given on the assumption that the eNB200-2 is decided as the target eNB by such handover determination.

In step S202, the MRN 300 inquires the eNB 200-2 of whether the eNB200-2 is able to respond to a handover request from the MRN 300 throughthe X2 interface. In addition, step S202 may be performed before stepS201.

In step S203, the eNB 200-2 notifies the MRN 300 of whether the eNB200-2 is able to respond to the handover request from the MRN 300through the X2 interface in response to the inquiry from the MRN 300.

Hereinafter, a description will be given on the assumption that the eNB200-2 is able to respond to the handover request from the MRN 300.

In step S204, the MRN 300 transmits a handover request for requestingthe acceptance for the MRN 300 to the eNB 200-2 through the X2interface. The handover request includes information indicating that atransmission source of the handover request is “MRN”. In general, thehandover request is transmitted, so that a preparation step(Preparation) in the handover procedure is started. Until the handoverprocedure is completed, the DeNB 200-1 is a “source eNB”.

In step S205, the eNB 200-2 determines whether to permit or reject thehandover request on the basis of the handover request from the MRN 300.Hereinafter, a description will be given on the assumption that the eNB200-2 determines to permit the handover request.

In step S206, the eNB 200-2 requests the DeNB 200-1 to transmitinformation for the handover of the MRN 300 through the X2 interface.

In step S207, the DeNB 200-1 transmits the information for the handoverof the MRN 300 to the eNB 200-2 through the X2 interface together with apermission response (Ack) for the request from the eNB 200-2. Theinformation for the handover of the MRN 300 includes X2 signalingcontext reference, S1 EPC signaling context reference, target cell ID,RRC context, AS configuration, E-RAB context and the like of the MRN300.

In step S208, the eNB 200-2 notifies, on the X2 interface, the MRN 300of information necessary for establishing a connection to the eNB 200-2together with a permission response (Ack) for the handover request fromthe MRN 300. The information necessary for communicating with the eNB200-2, for example, includes a new C-RNTI and security algorithmidentifier, dedicated RACH preamble and SIB as an option, and the like.

In step S209, the MRN 300 disconnects a connection to the DeNB 200-1 inresponse to the reception of a handover permission response from the eNB200-2. Then, the MRN 300 performs a process (a random access process, anRRC connection establishment process and the like) for establishing aconnection to the eNB 200-2 (step S212). Meanwhile, the DeNB 200-1performs a process (data forwarding) of forwarding data not to betransmitted to MRN 300 to the eNB 200-2 through the X2 interface (stepsS210 and S211).

In this way, when the handover procedure is completed, the eNB 200-2serves as a new DeNB of the MRN 300.

(2.1.2) Operation Pattern 2

FIG. 13 is a sequence diagram of the operation pattern 2 according tothe embodiment. Hereinafter, only differences from the operation pattern1 according to the present embodiment will be described.

As illustrated in FIG. 13, in the operation pattern 2, when transmittinga handover request to a target eNB 200-2, the MRN 300 transmitsinformation indicating a load state of the MRN 300 together with thehandover request (step S204-1).

The load state includes the number of UEs 100 accommodated by the MRN300 (specifically, the number of UEs 100 being connected to the MRN300), the amount of traffic dealt by the MRN 300, or the like. Inaddition, the load state may include a potential load state (forexample, processing capability such as the maximum number of UEs 100that may be accommodated or the maximum amount of traffic), as well asan actual load state.

After the information indicating the load state of the MRN 300 isreceived together with the handover request, the target eNB 200determines whether to permit the handover request on the basis of theinformation indicating the load state of the MRN 300 (step S205-1).

Specifically, the eNB 200-2 compares a margin based on its own loadstate with the load state of the MRN 300, and determines whether aproblem does not occur after a connection to the MRN 300 is established.

(2.1.3) Operation Pattern 3

In the operation pattern 3 according to the present embodiment, the MRN300 performs a process of adjusting a transmission timing of a handoverrequest before transmitting the handover request (step S204).

Specifically, when the movement speed of the MRN 300 exceeds a thresholdvalue, the MRN 300 adjusts the transmission timing of the handoverrequest to be advanced more than a normal timing. Furthermore, when themovement speed of the MRN 300 is equal to or less than the thresholdvalue, the MRN 300 returns the transmission timing of the handoverrequest to the normal timing.

For example, a case is considered, in which in the handoverdetermination (step S201), when a DeNB candidate with RSRP higher thanthat of the DeNB 200-1 during current connection exists on the DeNBlist, the MRN 300 decides the DeNB candidate as a target eNB. In such acase, when the movement speed of the MRN 300 exceeds the thresholdvalue, the MRN 300 corrects (offsets) the RSRP of the DeNB 200-1 duringcurrent connection to be low or corrects (offsets) the RSRP of the DeNBcandidate to be high, so that a trigger of handover easily occurs and ahandover request timing can be advanced.

Alternatively, a case is considered, in which in the handoverdetermination (step S201), when the RSRP of the DeNB candidate exceedsthe threshold value, the MRN 300 decides the DeNB candidate as a targeteNB. In such a case, the MRN 300 corrects (offsets) the RSRP of the DeNBcandidate to be high or lowers the threshold value, so that a trigger ofhandover easily occurs and a handover request timing can be advanced.

Furthermore, when the movement speed of the MRN 300 exceeds thethreshold value, the MRN 300 may transmit the handover request withoutinquiring the eNB 200-2 of whether the eNB 200-2 responds to thehandover request from the MRN 300 (step S202).

(2.1.4) Operation Pattern 4

In the operation pattern 4 according to the present embodiment, the MRN300 performs the handover determination (step S201) using a DeNB listwith additional information.

FIG. 14 is a configuration diagram of the DeNB list used in theoperation pattern 4. As illustrated in FIG. 14, the DeNB list used inthe operation pattern 4 includes information on the position, celldirection, capacity, and cell size of each (identifier of) DeNBcandidate.

The MRN 300 determines a target eNB on the basis of the DeNB list.Specifically, the MRN 300 decides whether the DeNB candidate isappropriate as the target eNB under (the whole or a part of) thefollowing conditions.

Firstly, when the position of the DeNB candidate coincides with themovement direction of the MRN 300, the MRN 300 determines that the DeNBcandidate is appropriate.

Secondly, when the cell direction (the cell formation position) of theDeNB candidate coincides with the movement direction of the MRN 300, theMRN 300 determines that the DeNB candidate is appropriate.

Thirdly, for the capacity of the DeNB candidate and the load state (thenumber of connections/traffic) of the MRN 300, when the load state iswithin the capacity range of the DeNB candidate, the MRN 300 determinesthat the DeNB candidate is appropriate.

Fourthly, for the size of a service area of the DeNB candidate and themovement speed of the MRN 300, when an area passage time of the DeNBcandidate is equal to or more than a constant reference, the MRN 300determines that the DeNB candidate is appropriate.

In addition, as an application, when there are no DeNB candidates, alist of the DeNB candidates may be updated. An operation in this casewill be described in a third embodiment.

Furthermore, in the present operation pattern, the case, in which theinformation on the position, the cell direction, the capacity, and thecell size is included in the DeNB list, was described. However, theinformation may be included in the neighboring eNB list. In this case,the neighboring eNB list includes information on the position, the celldirection, the capacity, and the cell size of (an identifier of) eacheNB. Then, the MRN 300 may perform the handover determination using theneighboring eNB list.

(2.2) Conclusion of Second Embodiment

As described above, in the mobile communication system in which the eNB200 performs determination regarding the handover of the UE 100connected to the eNB 200, the MRN 300, which is connected to the DeNB200-1 and performs relay transmission between the DeNB 200-1 and the UE100, performs determination regarding the handover of the MRN 300. Inthis way, the MRN 300 is able to perform optimal handover determinationin response to its own state or the state and the like of the DeNBcandidate. Furthermore, it is possible to perform the handoverdetermination without transmitting a measurement report from the MRN 300to the DeNB 200-1, so that it is possible to save a radio resource forthe measurement report.

The MRN 300 inquires the target eNB 200 of whether the target eNB 200 isable to respond to the handover request from the MRN 300. In this way,the MRN 300 confirms that the target eNB 200 is able to respond to itsown handover request, and then is able to transmit the handover requestto the target eNB 200.

The MRN 300 transmits the handover request to the target eNB 200 usingthe X2 interface established between the MRN 300 and the target eNB 200.In this way, it is possible to transmit the handover request from theMRN 300 to the target eNB 200 without performing the handoverdetermination by the DeNB 200-1, so that it is possible to reduce theload of the DeNB 200-1, and to quickly perform handover.

The handover request includes information indicating that a transmissionsource of the handover request is “MRN”. In this way, the target eNB 200recognizes that the transmission source of the handover request is“MRN”, and then is able to determine whether to permit the handoverrequest.

The target eNB 200 requests the DeNB 200-1 to transmit the informationfor the handover of the MRN 300 in response to the reception of thehandover request from the MRN 300. The DeNB 200-1 transmits theinformation for the handover of the MRN 300 to the target eNB 200 inresponse to the request from the target eNB 200. In this way, even whenthe handover of the MRN 300 is performed at the initiative of the MRN300, the target eNB 200 is able to acquire the information for thehandover of the MRN 300 from the DeNB 200-1.

The target eNB 200 receives the information for the handover of the MRN300 from. the DeNB 200-1, and then transmits a handover permissionresponse (Handover Request Ack) including the information for thehandover of the MRN 300 to the MRN 300 using the X2 interface. In thisway, it is possible to transmit the handover permission response fromthe target eNB 200 to the MRN 300 without performing the handoverdetermination by the DeNB 200-1, so that it is possible to reduce theload of the DeNB 200-1, and to quickly perform handover.

In the operation pattern 2, in the handover procedure of the MRN 300 tothe target eNB 200, when transmitting the handover request to the targeteNB 200, the MRN 300 transmits the information indicating the load stateof the MRN 300 together with the handover request. The target eNB 200receives the information indicating the load state of the MRN 300together with the handover request, and then determines whether topermit the handover request on the basis of the information indicatingthe load state of the MRN 300. In this way, the target eNB 200 is ableto determine whether to permit the handover request on the basis of itsown load state and the load state of the MRN 300.

In the operation pattern 3, the MRN 300 transmits the handover requestat the timing corresponding to its own movement speed. In this way, forexample, it is possible to reduce handover failure frequency when theMRN 300 moves at a high speed.

In the operation pattern 4, the MRN 300 decides the target eNB 200 onthe basis of the DeNB list that is a list of DeNB candidates. The DeNBlist includes information on at least one of the position, celldirection, capacity, and cell size of each DeNB candidate. In this way,the MRN 300 is able to decide whether the DeNB candidate is set as thetarget eNB in consideration of at least one of the position, celldirection, capacity, and cell size of the DeNB candidate.

(3) Third Embodiment

Hereinafter, the third embodiment will be described while focusing onthe differences from the aforementioned each embodiment. The presentembodiment corresponds to an application example of the secondembodiment.

(3.1) Operation According to Third Embodiment

Hereinafter, the operation of the mobile communication system accordingto the present embodiment will be described.

In the present embodiment, when it is not possible to perform thehandover of the MRN 300 to a DeNB candidate existing on the DeNB list,the MRN 300 acquires a DeNB list held by another MRN connected topredetermined eNB (a predetermined base station) from the other MRN.

Furthermore, as described in the operation pattern 4 of the secondembodiment, the “predetermined eNB” indicates a “current eNB” or a “DeNBcandidate existing on the DeNB list” when a DeNB candidate appropriateas a target eNB does not exist on the DeNB list. Alternatively, the“predetermined eNB” indicates the “target eNB” when the handover requestfrom the MRN 300 is rejected by the target eNB. The following operationpattern 1 corresponds to the former case and the following operationpattern 2 corresponds to the latter case.

(3.1.1) Operation pattern 1

FIG. 15 is a sequence diagram of an operation pattern 1 according to thepresent embodiment. Hereinafter, a description will be provided for thecase in which when a DeNB candidate appropriate as a target eNB does notexist on the DeNB list, an eNB 200-2 and eNB 200-3 serving as DeNBcandidates existing on the DeNB list are set as the “predetermined eNB”.Another MRN 1 (MRN 300-1) and another MRN 2 (MRN 300-2) are connected tothe eNB 200-2.

In step S301, the MRN 300 determines that all DeNB candidates existingon the DeNB list are not appropriate as the target eNB.

In step S302, the MRN 300 inquires the eNB 200-2 and the eNB 200-3serving as the DeNB candidates existing on the DeNB list of MRN (or RN)during connection through the X2 interface.

In step S303, the eNB 200-2 and the eNB 200-3 notify the MRN 300 of theMRN during connection through the X2interface. Furthermore, the eNB200-2 notifies the MRN 300 of an identifier of the MRN 300-1 and anidentifier of the MRN 300-2. The eNB 200-3 notifies the MRN 300 of thefact that there is no MRN during connection.

In step S304, the MRN 300 accesses the MRN 300-1 and the MRN 300-2through the X2 interface on the basis of the notification from the eNB200-2, and requests a DeNB list.

In step S305, each of the MRN 300-1 and the MRN 300-2 notifies (reports)the MRN 300 of a DeNB list held therein through the X2 interface.

In step S306, the MRN 300 checks a DeNB list held therein and the DeNBlists received from the MRN 300-1 and the MRN 300-2.

In step S307, the MRN 300 determines whether there is a differencebetween the DeNB list held therein and the DeNB lists received from theMRN 300-1 and the MRN 300-2. Specifically, the MRN 300 confirms whethera DeNB candidate not existing on the DeNB list held therein exists onthe DeNB lists received from the MRN 300-1 and the MRN 300-2.

When such a DeNB candidate exists (step S307; Yes), the MRN 300 updatesits own DeNB list such that the DeNB candidate is added in step S308.Specifically, the MRN 300 adds an identifier of the DeNB candidate toits own DeNB list. As a consequence, it is possible to start handover inwhich the DeNB candidate is set as the target eNB.

(3.1.2) Operation Pattern 2

FIG. 16 is a sequence diagram of an operation pattern 2 according to thepresent embodiment. Hereinafter, a description will be provided for thecase in which when the handover request from the MRN 300 is rejected bythe eNB 200-2, the eNB 200-2 is set as the “predetermined eNB”.

In step S311, the MRN 300 transmits the handover request to the eNB200-2 through the X2 interface.

In step S312, the eNB 200-2 determines whether to permit or reject thehandover request of the MRN 300. Hereinafter, a description will begiven on the assumption that the eNB 200-2 determined to reject thehandover request of the MRN 300.

In step S313, the eNB 200-2 notifies the MRN 300 of a handover negativeacknowledgement (Nack) and MRN (or RN) being connected to the eNB 200-2,through the X2 interface. Then, the same operations as those after stepS304 of the operation pattern 1 are performed.

(3.2) Conclusion of Third Embodiment

As described above, when it is not possible to perform the handover ofthe MRN 300 in which the DeNB candidate existing on the DeNB list is setas the target eNB 200, the MRN 300 acquires the DeNB list held byanother MRN connected to the eNB 200-2 existing on the DeNB list fromthe other MRN. Then, the MRN 300 decides a new target eNB from theacquired DeNB list. In this way, even when it is not possible to performthe handover of the MRN 300 in which the DeNB candidate existing on theDeNB list is set as the target eNB 200, it is possible to attempthandover to the new target eNB using the DeNB list held by the otherMRN.

In the present embodiment, the MRN 300 receives information on the otherMRN connected to the eNB 200-2 from the eNB 200-2. In this way, the MRN300 is able to recognize the other MRN connected to the eNB 200-2.

In the present embodiment, before the information on the other MRNconnected to the eNB 200-2 is received from the eNB 200-2, the MRN 300inquires the eNB 200-2 of the other MRN connected to the eNB 200-2. Inthis way, the eNB 200-2 is able to notify the MRN 300 of MRN connectedto the eNB 200-2 in response to the request from the MRN 300.

In the present embodiment, the eNB 200-2 notifies the MRN 300 of thehandover rejection response (Nack) for the MRN 300 and the informationon the MRN during connection. In this way, the MRN 300 is able torecognize the other MRN connected to the eNB 200-2.

(4) Fourth Embodiment

Hereinafter, the fourth embodiment will be described while focusing onthe differences from the aforementioned each embodiment.

In the aforementioned second embodiment and third embodiment, thehandover of the MRN 300 is performed at the initiative of the MRN 300.However, in the present embodiment, the handover of the MRN 300 isperformed at the initiative of the DeNB 200-1. That is, in the presentembodiment, the handover of the MRN 300 is performed by applying anormal handover procedure in the LTE.

(4.1) Operation According to Fourth Embodiment

Hereinafter, the operation of the mobile communication system accordingto the present embodiment will be described.

In the present embodiment, the DeNB 200-1 determines whether to performthe handover of the MRN 300 to eNB (a cell) existing on the neighboringeNB list on the basis of a measurement report from the MRN 300.Furthermore, even though there is eNB existing on the neighboring eNBlist, if the eNB does not have the DeNB function, it is meaningless toset the eNB as the target eNB. Thus, in the present embodiment, theneighboring eNB list is configured and managed as follows.

(4.1.1) Management of Neighboring eNB List

FIG. 17 is a configuration diagram of the neighboring eNB list accordingto the present embodiment.

As illustrated in FIG. 17, for (a cell ID (TCI) of) each neighboringeNB, the neighboring eNB list further includes information indicatingwhether the neighboring eNB has the DeNB function. For example, in theneighboring eNB having no DeNB function, a flag indicating that theneighboring eNB has no DeNB function is set. Other items are the same asthose of a neighboring eNB list (called a “neighboring relation table(NRT)”) of specifications. From the specifications, the neighboring eNBlist may be updated by an ANR (Automatic Neighbour Relation) function.

The eNB 200 (DeNB 200-1) acquires information on the neighboring eNBlist from the OAM 500 and manages the neighboring eNB list. In thepresent embodiment, when the MRN 300 is connected to the DeNB 200-1, theDeNB 200-1 requests the OAM 500 to transmit information for updating theneighboring eNB list. Then, the DeNB 200-1 updates the neighboring eNBlist in response to the information from the OAM 500.

(4.1.2) Handover Procedure

(4.1.2.1) Operation Pattern 1

FIG. 18 is a sequence diagram of an operation pattern 1 according to thepresent embodiment.

As illustrated in FIG. 18, in step S401, the MRN 300 transmits ameasurement report to the DeNB 200-1.

In step S402, the DeNB 200-1 designates neighboring eNBs having the DeNBfunction on the basis of the neighboring eNB list (NL or NRT).

In step S403, the DeNB 200-1 decides a target eNB from the neighboringeNBs designated in step 5402 on the basis of the measurement report fromthe MRN 300. For example, the DeNB 200-1 decides the neighboring eNB,which was designated in step S402 and has high RSRP indicated by themeasurement report, as the target eNB. Hereinafter, a description willbe given on the assumption that the eNB 200-2 is determined as thetarget eNB.

In step S404, the DeNB 200-1 transmits a handover request to the targeteNB 200-2 through the X2 interface.

In step S405, the target eNB 200-2 determines whether to permit orreject the handover request from the DeNB 200-1. Then, the normalhandover procedure is performed.

(4.1.2.2) Operation Pattern 2

FIG. 19 is a sequence diagram of an operation pattern 2 according to thepresent embodiment. Hereinafter, differences from the operation pattern1 according to the present embodiment will be described.

As illustrated in FIG. 19, in step S401-1, when transmitting themeasurement report to the DeNB 200-1, the MRN 300 notifies the DeNB200-1 of its own load state. However, the notification timing of theload state may be different from the timing of the measurement report.In addition, when the DeNB 200-1 has recognized the load state of theMRN 300, the notification of the load state of the MRN 30 to the DeNB200-1 may omit.

The load state includes the number of UEs 100 accommodated by the MRN300 (specifically, the number of UEs 100 being connected to the MRN300), the amount of traffic dealt by the MRN 300, or the like. Inaddition, the load state may include a potential load state (forexample, processing capability such as the maximum number of UEs 100that may be accommodated or the maximum amount of traffic), as well asan actual load state.

Step S402 and step S403 are equal to those of the operation pattern 1.

In step S404-1, when transmitting handover request to the target eNB200-2 through the X2 interface, the DeNB 200-1 notifies the DeNB 200-1of the load state of the MRN.

In step S405-1, the target eNB 200-2 determines whether to permit orreject the handover request from the DeNB 200-1 in consideration of theload state of the MRN. Specifically, the eNB 200-2 compares a marginbased on its own load state with the load state of the MRN 300, anddetermines whether a problem does not occur after a connection to theMRN 300 is established. Then, the normal handover procedure isperformed.

(4.2) Conclusion of Fourth Embodiment

As described above, for each neighboring eNB, the neighboring eNB listfurther includes the information indicating whether the neighboring eNBhas the DeNB function. In this way, the eNB 200 (the DeNB 200-1) is ableto decide the target eNB 200 from the neighboring eNBs having the DeNBfunction on the basis of the neighboring eNB list.

When the MRN 300 is connected to the DeNB 200-1, the DeNB 200-1 requeststhe OAM 500 to transmit the information for updating the neighboring eNBlist. Then, the DeNB 200-1 updates the neighboring eNB list in responseto the information from the OAM 500. In this way, before the handover ofthe MRN 300 is generated, it is possible to allow the neighboring eNBlist to be in the latest state.

In the case in which the handover request from the DeNB 200-1 hasreceived, when the target eNB 200 does not have the DeNB function, thetarget eNB 200 transmits information indicating the fact that the targeteNB 200 does not have the DeNB function to the DeNB 200-1, together witha rejection response for the handover request. Then, the DeNB 200-1updates the neighboring eNB list in response to the reception of theinformation indicating the fact that the target eNB 200 does not haveDeNB function from the target eNB 200. In this way, it is possible tocorrect the neighboring eNB list using the handover procedure.

In the operation pattern 2, the DeNB 200-1 transmits the informationindicating the load state of the MRN 300 to the target eNB 200, togetherwith the handover request. The target eNB 200 receives the informationindicating the load state of the MRN 300 together with the handoverrequest, and then determines whether to permit the handover request onthe basis of the information indicating the load state of the MRN 300.In this way, the target eNB 200 is able to determine whether to permitthe handover request on the basis of its own load state and the loadstate of the MRN 300.

(5) Fifth Embodiment

Hereinafter, the fifth embodiment will be described while focusing onthe differences from the aforementioned each embodiment.

In the present embodiment, the handover procedure according to theaforementioned second embodiment, that is, the handover of the MRN 300is basically performed at the initiative of the MRN 300 and the DeNB200-1 also performs handover determination as with the aforementionedfourth embodiment.

(5.1) Operation According to Fifth Embodiment

FIG. 20 is an operation sequence diagram according to the presentembodiment. In an initial state of the present sequence, it is assumedthat the MRN 300 is performing relay transmission by connection to theDeNB 200-1.

As illustrated in FIG. 20, in step S501, the MRN 300 checks ameasurement result of a received reference signal and a held DeNB list.

In step S502, the MRN 300 performs handover determination in response toa check result in step S501. For example, when a DeNB candidate withRSRP higher than that of a DeNB 200-1 during current connection existson the DeNB list, the MRN 300 decides the DeNB candidate as a targeteNB.

Hereinafter, a description will be given on the assumption that the eNB200-2 is determined as the target eNB by such handover determination.However, one or a plurality of target eNBs may be determined in stepS502.

In step S503, the MRN 300 inquires the DeNB 200-1 of whether the DeNB200-1 is able to respond to a handover request from the MRN 300. Inaddition, step S503 may be performed before step S502.

In step S504, the DeNB 200-1 inquires the MRN 300 of whether the DeNB200-1 is able to respond to the handover request from the MRN 300 inresponse to the inquiry from the MRN 300.

Hereinafter, a description will be given on the assumption that the DeNB200-1 is able to respond to the handover request from the MRN 300.

In step S505, the MRN 300 transmits a handover request for requestinghandover to the eNB 200-2 to the DeNB 200-1 through the X2 interface.The handover request includes an identifier of the eNB 200-2. When thereare a plurality of target eNBs, the handover request includesidentifiers of the plurality of target eNBs. Furthermore, the handoverrequest may include information indicating that a transmission source ofthe handover request is “MRN”.

In step S506, the DeNB 200-1 determines whether handover is possible foreach target eNB 200 on the basis of (the identifier included in) thehandover request from the MRN 300. For example, as described in thefourth embodiment, it is possible to perform determination on the basisof the presence or absence of the DeNB function.

Hereinafter, a description will be given on the assumption that the DeNB200-1 determined that handover to the target eNB 200 is possible.

In step S507, the DeNB 200-1 transmits the handover request to thetarget eNB 200-2 through the X2 interface.

In step S508, the target eNB 200-2 determines whether to permit orreject the handover request from the DeNB 200-1. Then, the normalhandover procedure is performed.

In addition, also in the present embodiment, it is possible to considerthe load state of the MRN 300 similarly to the operation pattern 2according to the fourth embodiment.

Furthermore, the handover procedure according to the present embodimentand the handover procedure according to the second embodiment may beseparately used. For example, when the DeNB 200-1 responds to thehandover request from the MRN 300 and the target eNB 200-2 does notrespond to the handover request from the MRN 300, the handover procedureaccording to the present embodiment may be applied. Alternatively, whenan elapsed time from the update of the DeNB list held by the MRN 300 iswithin a threshold value, the handover procedure according to the secondembodiment may be applied, and when the elapsed time exceeds thethreshold value, the handover procedure according to the presentembodiment may be applied.

(5.2) Conclusion of Fifth Embodiment

As described above, in the mobile communication system in which the eNB200 performs determination regarding the handover of the UE 100connected to the eNB 200, the MRN 300, which is connected to the DeNB200-1 and performs relay transmission between the DeNB 200-1 and the UE100, performs determination regarding the handover of the MRN 300. Inthis way, the MRN 300 is able to perform optimal handover determinationin response to its own state, that is, a situation unique to the MRN300.

The MRN 300 allows one identifier or a plurality of identifiers of thetarget eNB 200 to be included in the handover request and then transmitsthe handover request to the DeNB 200-1. The DeNB 200-1 determineswhether handover is possible for each target eNB 200 on the basis of thehandover request from the MRN 300. In this way, the DeNB 200-1 is ableto determine whether the target eNB 200 determined by the MRN 300 isappropriate. Consequently, it is possible to determine the target eNB200 more appropriately.

In the present embodiment, the MRN 300 inquires the DeNB 200-1 ofwhether the DeNB 200-1 is able to respond to the handover request fromthe MRN 300. In this way, after confirming that the DeNB 200-1 is ableto respond to the handover request from the MRN 300, it is possible totransmit the handover request from the MRN 300 to the DeNB 200-1.

(6) Other Embodiments

It should not be understood that those descriptions and drawingsconstituting a part of the present disclosure limit the presentdisclosure. Further, various substitutions, examples, or operationaltechniques shall be apparent to a person skilled in the art on the basisof this disclosure.

The aforementioned first embodiment to fifth embodiment may be performedseparately and independently and may also be performed through acombination thereof. For example, the DeNB list acquisition methoddescribed in the third embodiment may be applied to the fifthembodiment.

In the aforementioned each embodiment, the MRN 300 serving as a movablerelay station was described as an example, and the present disclosuremay also be applied to an unmovable relay station. For example, when anew eNB is installed in the vicinity of the relay station or when anexisting eNB stops its own operation, since a peripheral situation ofthe relay station is changed, it may be necessary to update the DeNBlist (DL) and the neighboring eNB list (NL or NRT) or perform thehandover of the relay station.

INDUSTRIAL APPLICABILITY

As described above, the communication control method according to thepresent disclosure can support a movable relay station and thus, thepresent disclosure is useful in a radio communication field.

1. A communication method comprising: receiving from a base station, bya first communication apparatus, first information indicating that thebase station supports a relay apparatus configured to relay trafficbetween the base station and another communication apparatus;transmitting to the base station, by the first communication apparatus,after receiving the first information from the base station, secondinformation indicating that the first communication apparatus is therelay apparatus; and transmitting to the base station, by the firstcommunication apparatus, third information indicating expected dataamount of the first communication apparatus.
 2. A first communicationapparatus, comprising: a processor and a memory coupled to theprocessor, the processor configured to perform processes of: receiving,from a base station, first information indicating that the base stationsupports a relay apparatus configured to relay traffic between the basestation and another communication apparatus; after receiving the firstinformation from the base station, transmitting to the base station,second information indicating that the first communication apparatus isthe relay apparatus; and transmitting to the base station, thirdinformation indicating expected data amount of the first communicationapparatus.
 3. A base station comprising: a processor and a memorycoupled to the processor, the processor configured to perform processesof: transmitting to a first communication apparatus, first informationindicating that the base station supports a relay apparatus configuredto relay traffic between the base station and another communicationapparatus; after transmitting the first information, receiving from thefirst communication apparatus, second information indicating that thefirst communication apparatus is the relay apparatus; and receiving fromthe first communication apparatus, third information indicating expecteddata amount of the first communication apparatus.
 4. A chipset includedin a first communication apparatus, the chipset comprising: a processorand a memory coupled to the processor, the processor configured toperform processes of: receiving, from a base station, first informationindicating that the base station supports a relay apparatus configuredto relay traffic between the base station and another communicationapparatus; after receiving the first information from the base station,transmitting to the base station, second information indicating that thefirst communication apparatus is the relay apparatus; and transmittingto the base station, third information indicating expected data amountof the first communication apparatus.